Building management system with point virtualization for online meters

ABSTRACT

A building management system includes a meter configured to provide data samples of a real point. The real point corresponds to a first physical parameter measured by the meter. The building management system also includes an analytics circuit configured to store a real point object representing the real point and store a meter object representing the meter. The meter object includes a points attribute that lists one or more point objects associated with the meter object including at least the real point object. The analytics circuit is also configured to store a virtual point object representing a virtual point. The virtual point corresponds to a second physical parameter not measured by the meter. The analytics circuit is also configured to update the points attribute in the meter object to list the virtual point object as one of the point objects associated with the meter object.

CROSS-REFERENCE TO RELATED PATENT APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/052,083, filed Aug. 1, 2018, which claims the benefit of and priorityto Indian Provisional Patent Application No. 201741040781, filed Nov.15, 2017, both of which are incorporated by reference herein in theirentireties.

BACKGROUND

The present disclosure relates generally to a building management system(BMS) and more particularly to a BMS with point virtualization foronline meters. A BMS is, in general, a system of devices configured tocontrol, monitor, and manage equipment in or around a building orbuilding area. A BMS can include, for example, a HVAC system, a securitysystem, a lighting system, a fire alerting system, any other system thatis capable of managing building functions or devices, or any combinationthereof.

A BMS typically monitors multiple facilities and/or buildings within aportfolio using meters that provide live or real-time data samples tothe BMS relating to conditions of the building and/or building equipmentthat serves the building. Each meter may provide one or more pointscorresponding to physical parameters (e.g., voltage, current,temperature, demand, consumption) to the BMS. The BMS relies on metersto provide data samples of the points, and uses the data to generatemetrics, key performance indictors (KPIs), graphical representations ofbuilding equipment operation, etc. to deliver to customers. High-endmeters may be compatible with BMS networks (e.g., BACnet, InternetProtocol) and may provide multiple points via a single meter, but may becost prohibitive for many potential BMS customers. Lower-cost oralready-installed metering infrastructure generally includes meterswhich provide only one or two points. The low-cost meters may notprovide enough points to make use of many BMS analytics and features. Analternative to adding new, physical meters is simulating virtual pointswithin the BMS.

SUMMARY

One implementation of the present disclosure is a building managementsystem. The building management system includes a meter configured toprovide data samples of a real point. The real point corresponds to afirst physical parameter measured by the meter. The building managementsystem also includes an analytics circuit configured to store a realpoint object representing the real point and store a meter objectrepresenting the meter. The meter object includes a points attributethat lists one or more point objects associated with the meter objectincluding at least the real point object. The analytics circuit is alsoconfigured to store a virtual point object representing a virtual point.The virtual point corresponds to a second physical parameter notmeasured by the meter. The analytics circuit is also configured toupdate the points attribute in the meter object to list the virtualpoint object as one of the point objects associated with the meterobject, receive a data sample of the real point from the meter,calculate a value of the virtual point, and calculate a metric based onthe data sample of the real point and the value of the virtual point.The building management system also includes a system manager configuredto control building equipment using the metric to affect the firstphysical parameter and the second physical parameter.

In some embodiments, the analytics circuit is configured to calculatethe value of the virtual point using a formula stored in the virtualpoint object. In some embodiments, the analytics circuit is configuredto calculate the value of the virtual point using a formula stored inthe virtual point object. In some embodiments, the formula defines thevalue of the virtual point as a function of the data sample of the realpoint. In some embodiments, the first physical parameter and the secondphysical parameter characterize operation of the building equipment.

In some embodiments, the analytics circuit is further configured togenerate a graphical user interface that includes a graphicalrepresentation of the operation of the building equipment. The graphicalrepresentation is generated based on the data sample of the real pointand the value of the virtual point. In some embodiments, the graphicaluser interface comprises a first indicator identifying the real point asreal and a second indicator identifying the virtual point as virtual.

Another implementation of the present disclosure is a method formanaging a building. The method includes collecting, by a meter, datasamples of a real point. The real point corresponds to a first physicalparameter measured by the meter. The method includes storing a realpoint object representing the real point and storing a meter objectrepresenting the meter. The meter object includes a points attributethat lists one or more point objects associated with the meter objectincluding at least the real point object. The method includes storing avirtual point object representing a virtual point. The virtual pointcorresponds to a second physical parameter not measured by the meter.The method includes updating the points attribute in the meter object tolist the virtual point object in as one of the point objects associatedwith the meter object, receiving a data sample of the real point fromthe meter, calculating a value of the virtual point, calculating ametric based on the data sample of the real point and the value of thevirtual point, and controlling, based on the metric, building equipmentto affect the first physical parameter and the second physicalparameter.

In some embodiments, calculating the value of the virtual point includesstoring a formula in the virtual point object and calculating the valueusing the formula. In some embodiments, the method includes generating agraphical user interface that allows the user to input the formula. Insome embodiments, the formula defines the value of the virtual point asa function of the data sample for the real point. In some embodiments,the first physical parameter and the second physical parametercharacterize operation of the building equipment.

In some embodiments, the method includes generating a graphical userinterface that includes a graphical representation of the operation ofthe building equipment based on the data sample of the real point andthe value of the virtual point. In some embodiments, the method includesproviding, on the graphical user interface, a first indicatoridentifying the real point as real and a second indicator identifyingthe virtual point as virtual.

Another implementation of the present disclosure is a buildingmanagement system. The building management system includes buildingequipment operable to affect a variable state or condition of abuilding, a plurality of meters configured to collect data samples of aplurality of real points relating to an operation of the buildingequipment, and an analytics circuit configured to generate a graphicaluser interface. The graphical user interface includes a points treewidget comprising a list of the plurality of real points, a meterdistribution tree widget comprising a list of the plurality of meters,and a meter details widget configured to allow a user to add a virtualpoint to the list of real points. The analytics circuit is alsoconfigured to receive data samples of the plurality of real points,calculate a value of the virtual point, and calculate a metric based onthe data samples of the plurality of real points and the value of thevirtual point. The building management system also includes a systemmanager configured to control the building equipment based on themetric.

In some embodiments, the graphical user interface includes a virtualpoint definition widget configured to allow a user to input a formulathat defines the virtual point. In some embodiments, the analyticscircuit is configured to generate the value of the virtual point usingthe formula and a first data sample of a first real point of theplurality of real points. In some embodiments, the analytics circuit isconfigured to generate a graphical representation of an operation of thebuilding equipment using the formula and the data samples of theplurality of real points.

In some embodiments, the virtual point definition widget comprises aformula field and a list of the plurality of real points. Each realpoint on the list of real points is selectable to add the real point tothe formula field. The virtual point definition widget also includes aplurality of operator buttons. Each operator button is selectable to addan operator to the formula field. The formula includes one or more realpoints and one or more operators to define the virtual point as afunction of the one or more real points. In some embodiments, theanalytics circuit is configured to check the formula input by the userfor syntax errors.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a HVAC system, accordingto some embodiments.

FIG. 2 is a block diagram of a waterside system which can be used toserve the building of FIG. 1, according to some embodiments.

FIG. 3 is a block diagram of an airside system which can be used toserve the building of FIG. 1, according to some embodiments.

FIG. 4 is a block diagram of a building management system (BMS) whichcan be used to monitor and control the building of FIG. 1, according tosome embodiments.

FIG. 5 is a block diagram of another BMS which can be used to monitorand control the building of FIG. 1, according to some embodiments.

FIG. 6 is a block diagram of a BMS with a point virtualization circuit608, according to some embodiments.

FIG. 7 is a block diagram of an object database 606 which can be used inthe BMSs of FIGS. 4-5, according to some embodiments.

FIG. 8 is a flowchart of a process for point virtualization under onlinemeters, according to some embodiments.

FIG. 9 is a depiction of a meter configuration interface which can begenerated by the BMS of FIG. 6, according to some embodiments.

FIG. 10 is a depiction of virtual point definition widget which can begenerated by the BMS of FIG. 6, according to some embodiments.

FIG. 11 is a depiction of a building scorecard dashboard which can begenerated by the BMS of FIG. 6, according to some embodiments.

DETAILED DESCRIPTION Building HVAC Systems and Building ManagementSystems

Referring now to FIGS. 1-5, several building management systems (BMS)and HVAC systems in which the systems and methods of the presentdisclosure can be implemented are shown, according to some embodiments.In brief overview, FIG. 1 shows a building 10 equipped with a HVACsystem 100. FIG. 2 is a block diagram of a waterside system 200 whichcan be used to serve building 10. FIG. 3 is a block diagram of anairside system 300 which can be used to serve building 10. FIG. 4 is ablock diagram of a BMS which can be used to monitor and control building10. FIG. 5 is a block diagram of another BMS which can be used tomonitor and control building 10.

Building and HVAC System

Referring particularly to FIG. 1, a perspective view of a building 10 isshown. Building 10 is served by a BMS. A BMS is, in general, a system ofdevices configured to control, monitor, and manage equipment in oraround a building or building area. A BMS can include, for example, aHVAC system, a security system, a lighting system, a fire alertingsystem, any other system that is capable of managing building functionsor devices, or any combination thereof.

The BMS that serves building 10 includes a HVAC system 100. HVAC system100 can include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 mayprovide a heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 may use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which can be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 may use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and may circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 can be located inor around building 10 (as shown in FIG. 1) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid can be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 may add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 may place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104can be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow can be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 may transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 can include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid may then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and mayprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 can include dampers or other flow control elements thatcan be operated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 116 orother flow control elements. AHU 106 can include various sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 may receive input from sensorslocated within AHU 106 and/or within the building zone and may adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve setpoint conditions for the building zone.

Waterside System

Referring now to FIG. 2, a block diagram of a waterside system 200 isshown, according to some embodiments. In various embodiments, watersidesystem 200 may supplement or replace waterside system 120 in HVAC system100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, waterside system 200 can include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and may operate to supply a heated or chilledfluid to AHU 106. The HVAC devices of waterside system 200 can belocated within building 10 (e.g., as components of waterside system 120)or at an offsite location such as a central plant.

In FIG. 2, waterside system 200 is shown as a central plant having aplurality of subplants 202-212. Subplants 202-212 are shown to include aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve thermal energy loads (e.g.,hot water, cold water, heating, cooling, etc.) of a building or campus.For example, heater subplant 202 can be configured to heat water in ahot water loop 214 that circulates the hot water between heater subplant202 and building 10. Chiller subplant 206 can be configured to chillwater in a cold water loop 216 that circulates the cold water betweenchiller subplant 206 building 10. Heat recovery chiller subplant 204 canbe configured to transfer heat from cold water loop 216 to hot waterloop 214 to provide additional heating for the hot water and additionalcooling for the cold water. Condenser water loop 218 may absorb heatfrom the cold water in chiller subplant 206 and reject the absorbed heatin cooling tower subplant 208 or transfer the absorbed heat to hot waterloop 214. Hot TES subplant 210 and cold TES subplant 212 may store hotand cold thermal energy, respectively, for subsequent use.

Hot water loop 214 and cold water loop 216 may deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air can bedelivered to individual zones of building 10 to serve thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) can be used inplace of or in addition to water to serve thermal energy loads. In otherembodiments, subplants 202-212 may provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 200are within the teachings of the present disclosure.

Each of subplants 202-212 can include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 202 is shown to include a plurality of heating elements 220(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 214. Heater subplant 202 is also shown toinclude several pumps 222 and 224 configured to circulate the hot waterin hot water loop 214 and to control the flow rate of the hot waterthrough individual heating elements 220. Chiller subplant 206 is shownto include a plurality of chillers 232 configured to remove heat fromthe cold water in cold water loop 216. Chiller subplant 206 is alsoshown to include several pumps 234 and 236 configured to circulate thecold water in cold water loop 216 and to control the flow rate of thecold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality ofheat recovery heat exchangers 226 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 216 to hot water loop214. Heat recovery chiller subplant 204 is also shown to include severalpumps 228 and 230 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 226 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 238 configured to remove heat from the condenser water incondenser water loop 218. Cooling tower subplant 208 is also shown toinclude several pumps 240 configured to circulate the condenser water incondenser water loop 218 and to control the flow rate of the condenserwater through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configuredto store the hot water for later use. Hot TES subplant 210 may alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 242. Cold TES subplant 212is shown to include cold TES tanks 244 configured to store the coldwater for later use. Cold TES subplant 212 may also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines inwaterside system 200 include an isolation valve associated therewith.Isolation valves can be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 200. In various embodiments, waterside system 200 can includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 200 and the types of loadsserved by waterside system 200.

Airside System

Referring now to FIG. 3, a block diagram of an airside system 300 isshown, according to some embodiments. In various embodiments, airsidesystem 300 may supplement or replace airside system 130 in HVAC system100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, airside system 300 can include a subsetof the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116,ducts 112-114, fans, dampers, etc.) and can be located in or aroundbuilding 10. Airside system 300 may operate to heat or cool an airflowprovided to building 10 using a heated or chilled fluid provided bywaterside system 200.

In FIG. 3, airside system 300 is shown to include an economizer-type airhandling unit (AHU) 302. Economizer-type AHUs vary the amount of outsideair and return air used by the air handling unit for heating or cooling.For example, AHU 302 may receive return air 304 from building zone 306via return air duct 308 and may deliver supply air 310 to building zone306 via supply air duct 312. In some embodiments, AHU 302 is a rooftopunit located on the roof of building 10 (e.g., AHU 106 as shown inFIG. 1) or otherwise positioned to receive both return air 304 andoutside air 314. AHU 302 can be configured to operate exhaust air damper316, mixing damper 318, and outside air damper 320 to control an amountof outside air 314 and return air 304 that combine to form supply air310. Any return air 304 that does not pass through mixing damper 318 canbe exhausted from AHU 302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 can be operated by an actuator. For example,exhaust air damper 316 can be operated by actuator 324, mixing damper318 can be operated by actuator 326, and outside air damper 320 can beoperated by actuator 328. Actuators 324-328 may communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 mayreceive control signals from AHU controller 330 and may provide feedbacksignals to AHU controller 330. Feedback signals can include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat can be collected, stored, or used by actuators 324-328. AHUcontroller 330 can be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil334, a heating coil 336, and a fan 338 positioned within supply air duct312. Fan 338 can be configured to force supply air 310 through coolingcoil 334 and/or heating coil 336 and provide supply air 310 to buildingzone 306. AHU controller 330 may communicate with fan 338 viacommunications link 340 to control a flow rate of supply air 310. Insome embodiments, AHU controller 330 controls an amount of heating orcooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and may return thechilled fluid to waterside system 200 via piping 344. Valve 346 can bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 may receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and may return the heatedfluid to waterside system 200 via piping 350. Valve 352 can bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 can be controlled by an actuator. Forexample, valve 346 can be controlled by actuator 354 and valve 352 canbe controlled by actuator 356. Actuators 354-356 may communicate withAHU controller 330 via communications links 358-360. Actuators 354-356may receive control signals from AHU controller 330 and may providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 may also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a setpoint temperature for supplyair 310 or to maintain the temperature of supply air 310 within asetpoint temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU 330 maycontrol the temperature of supply air 310 and/or building zone 306 byactivating or deactivating coils 334-336, adjusting a speed of fan 338,or a combination of both.

Still referring to FIG. 3, airside system 300 is shown to include abuilding management system (BMS) controller 366 and a client device 368.BMS controller 366 can include one or more computer systems (e.g.,servers, supervisory controllers, subsystem controllers, etc.) thatserve as system level controllers, application or data servers, headnodes, or master controllers for airside system 300, waterside system200, HVAC system 100, and/or other controllable systems that servebuilding 10. BMS controller 366 may communicate with multiple downstreambuilding systems or subsystems (e.g., HVAC system 100, a securitysystem, a lighting system, waterside system 200, etc.) via acommunications link 370 according to like or disparate protocols (e.g.,LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMScontroller 366 can be separate (as shown in FIG. 3) or integrated. In anintegrated implementation, AHU controller 330 can be a software moduleconfigured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, setpoints, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 may provide BMScontroller 366 with temperature measurements from temperature sensors362-364, equipment on/off states, equipment operating capacities, and/orany other information that can be used by BMS controller 366 to monitoror control a variable state or condition within building zone 306.

Client device 368 can include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 can be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 can be a stationary terminal or amobile device. For example, client device 368 can be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 may communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Building Management Systems

Referring now to FIG. 4, a block diagram of a building management system(BMS) 400 is shown, according to some embodiments. BMS 400 can beimplemented in building 10 to automatically monitor and control variousbuilding functions. BMS 400 is shown to include BMS controller 366 and aplurality of building subsystems 428. Building subsystems 428 are shownto include a building electrical subsystem 434, an informationcommunication technology (ICT) subsystem 436, a security subsystem 438,a HVAC subsystem 440, a lighting subsystem 442, a lift/escalatorssubsystem 432, and a fire safety subsystem 430. In various embodiments,building subsystems 428 can include fewer, additional, or alternativesubsystems. For example, building subsystems 428 may also oralternatively include a refrigeration subsystem, an advertising orsignage subsystem, a cooking subsystem, a vending subsystem, a printeror copy service subsystem, or any other type of building subsystem thatuses controllable equipment and/or sensors to monitor or controlbuilding 10. In some embodiments, building subsystems 428 includewaterside system 200 and/or airside system 300, as described withreference to FIGS. 2-3.

Each of building subsystems 428 can include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 can include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3.For example, HVAC subsystem 440 can include a chiller, a boiler, anynumber of air handling units, economizers, field controllers,supervisory controllers, actuators, temperature sensors, and otherdevices for controlling the temperature, humidity, airflow, or othervariable conditions within building 10. Lighting subsystem 442 caninclude any number of light fixtures, ballasts, lighting sensors,dimmers, or other devices configured to controllably adjust the amountof light provided to a building space. Security subsystem 438 caninclude occupancy sensors, video surveillance cameras, digital videorecorders, video processing servers, intrusion detection devices, accesscontrol devices and servers, or other security-related devices.

Still referring to FIG. 4, BMS controller 366 is shown to include acommunications interface 407 and a BMS interface 409. Interface 407 mayfacilitate communications between BMS controller 366 and externalapplications (e.g., monitoring and reporting applications 422,enterprise control applications 426, remote systems and applications444, applications residing on client devices 448, etc.) for allowinguser control, monitoring, and adjustment to BMS controller 366 and/orsubsystems 428. Interface 407 may also facilitate communications betweenBMS controller 366 and client devices 448. BMS interface 409 mayfacilitate communications between BMS controller 366 and buildingsubsystems 428 (e.g., HVAC, lighting security, lifts, powerdistribution, business, etc.).

Interfaces 407, 409 can be or include wired or wireless communicationsinterfaces (e.g., jacks, antennas, transmitters, receivers,transceivers, wire terminals, etc.) for conducting data communicationswith building subsystems 428 or other external systems or devices. Invarious embodiments, communications via interfaces 407, 409 can bedirect (e.g., local wired or wireless communications) or via acommunications network 446 (e.g., a WAN, the Internet, a cellularnetwork, etc.). For example, interfaces 407, 409 can include an Ethernetcard and port for sending and receiving data via an Ethernet-basedcommunications link or network. In another example, interfaces 407, 409can include a Wi-Fi transceiver for communicating via a wirelesscommunications network. In another example, one or both of interfaces407, 409 can include cellular or mobile phone communicationstransceivers. In one embodiment, communications interface 407 is a powerline communications interface and BMS interface 409 is an Ethernetinterface. In other embodiments, both communications interface 407 andBMS interface 409 are Ethernet interfaces or are the same Ethernetinterface.

Still referring to FIG. 4, BMS controller 366 is shown to include aprocessing circuit 404 including a processor 406 and memory 408.Processing circuit 404 can be communicably connected to BMS interface409 and/or communications interface 407 such that processing circuit 404and the various components thereof can send and receive data viainterfaces 407, 409. Processor 406 can be implemented as a generalpurpose processor, an application specific integrated circuit (ASIC),one or more field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents.

Memory 408 (e.g., memory, memory unit, storage device, etc.) can includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers and modules described in thepresent application. Memory 408 can be or include volatile memory ornon-volatile memory. Memory 408 can include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present application. According to someembodiments, memory 408 is communicably connected to processor 406 viaprocessing circuit 404 and includes computer code for executing (e.g.,by processing circuit 404 and/or processor 406) one or more processesdescribed herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various otherembodiments BMS controller 366 can be distributed across multipleservers or computers (e.g., that can exist in distributed locations).Further, while FIG. 4 shows applications 422 and 426 as existing outsideof BMS controller 366, in some embodiments, applications 422 and 426 canbe hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is shown to include an enterpriseintegration layer 410, an automated measurement and validation (AM&V)layer 412, a demand response (DR) layer 414, a fault detection anddiagnostics (FDD) layer 416, an integrated control layer 418, and abuilding subsystem integration later 420. Layers 410-420 can beconfigured to receive inputs from building subsystems 428 and other datasources, determine optimal control actions for building subsystems 428based on the inputs, generate control signals based on the optimalcontrol actions, and provide the generated control signals to buildingsubsystems 428. The following paragraphs describe some of the generalfunctions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 can be configured to serve clients orlocal applications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 can be configured to provide subsystem-spanning controlto a graphical user interface (GUI) or to any number of enterprise-levelbusiness applications (e.g., accounting systems, user identificationsystems, etc.). Enterprise control applications 426 may also oralternatively be configured to provide configuration GUIs forconfiguring BMS controller 366. In yet other embodiments, enterprisecontrol applications 426 can work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 can be configured to managecommunications between BMS controller 366 and building subsystems 428.For example, building subsystem integration layer 420 may receive sensordata and input signals from building subsystems 428 and provide outputdata and control signals to building subsystems 428. Building subsystemintegration layer 420 may also be configured to manage communicationsbetween building subsystems 428. Building subsystem integration layer420 translate communications (e.g., sensor data, input signals, outputsignals, etc.) across a plurality of multi-vendor/multi-protocolsystems.

Demand response layer 414 can be configured to optimize resource usage(e.g., electricity use, natural gas use, water use, etc.) and/or themonetary cost of such resource usage in response to satisfy the demandof building 10. The optimization can be based on time-of-use prices,curtailment signals, energy availability, or other data received fromutility providers, distributed energy generation systems 424, fromenergy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or fromother sources. Demand response layer 414 may receive inputs from otherlayers of BMS controller 366 (e.g., building subsystem integration layer420, integrated control layer 418, etc.). The inputs received from otherlayers can include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs may also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to some embodiments, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses can include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changingsetpoints, or activating/deactivating building equipment or subsystemsin a controlled manner. Demand response layer 414 may also includecontrol logic configured to determine when to utilize stored energy. Forexample, demand response layer 414 may determine to begin using energyfrom energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control moduleconfigured to actively initiate control actions (e.g., automaticallychanging setpoints) which minimize energy costs based on one or moreinputs representative of or based on demand (e.g., price, a curtailmentsignal, a demand level, etc.). In some embodiments, demand responselayer 414 uses equipment models to determine an optimal set of controlactions. The equipment models can include, for example, thermodynamicmodels describing the inputs, outputs, and/or functions performed byvarious sets of building equipment. Equipment models may representcollections of building equipment (e.g., subplants, chiller arrays,etc.) or individual devices (e.g., individual chillers, heaters, pumps,etc.).

Demand response layer 414 may further include or draw upon one or moredemand response policy definitions (e.g., databases, XML, files, etc.).The policy definitions can be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs can be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions canspecify which equipment can be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what setpoints can be changed, what the allowable setpoint adjustment range is, how long to hold a high demand setpointbefore returning to a normally scheduled setpoint, how close to approachcapacity limits, which equipment modes to utilize, the energy transferrates (e.g., the maximum rate, an alarm rate, other rate boundaryinformation, etc.) into and out of energy storage devices (e.g., thermalstorage tanks, battery banks, etc.), and when to dispatch on-sitegeneration of energy (e.g., via fuel cells, a motor generator set,etc.).

Integrated control layer 418 can be configured to use the data input oroutput of building subsystem integration layer 420 and/or demandresponse later 414 to make control decisions. Due to the subsystemintegration provided by building subsystem integration layer 420,integrated control layer 418 can integrate control activities of thesubsystems 428 such that the subsystems 428 behave as a singleintegrated supersystem. In some embodiments, integrated control layer418 includes control logic that uses inputs and outputs from a pluralityof building subsystems to provide greater comfort and energy savingsrelative to the comfort and energy savings that separate subsystemscould provide alone. For example, integrated control layer 418 can beconfigured to use an input from a first subsystem to make anenergy-saving control decision for a second subsystem. Results of thesedecisions can be communicated back to building subsystem integrationlayer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 can be configured toenhance the effectiveness of demand response layer 414 by enablingbuilding subsystems 428 and their respective control loops to becontrolled in coordination with demand response layer 414. Thisconfiguration may advantageously reduce disruptive demand responsebehavior relative to conventional systems. For example, integratedcontrol layer 418 can be configured to assure that a demandresponse-driven upward adjustment to the setpoint for chilled watertemperature (or another component that directly or indirectly affectstemperature) does not result in an increase in fan energy (or otherenergy used to cool a space) that would result in greater total buildingenergy use than was saved at the chiller.

Integrated control layer 418 can be configured to provide feedback todemand response layer 414 so that demand response layer 414 checks thatconstraints (e.g., temperature, lighting levels, etc.) are properlymaintained even while demanded load shedding is in progress. Theconstraints may also include setpoint or sensed boundaries relating tosafety, equipment operating limits and performance, comfort, fire codes,electrical codes, energy codes, and the like. Integrated control layer418 is also logically below fault detection and diagnostics layer 416and automated measurement and validation layer 412. Integrated controllayer 418 can be configured to provide calculated inputs (e.g.,aggregations) to these higher levels based on outputs from more than onebuilding subsystem.

Automated measurement and validation (AM&V) layer 412 can be configuredto verify that control strategies commanded by integrated control layer418 or demand response layer 414 are working properly (e.g., using dataaggregated by AM&V layer 412, integrated control layer 418, buildingsubsystem integration layer 420, FDD layer 416, or otherwise). Thecalculations made by AM&V layer 412 can be based on building systemenergy models and/or equipment models for individual BMS devices orsubsystems. For example, AM&V layer 412 may compare a model-predictedoutput with an actual output from building subsystems 428 to determinean accuracy of the model.

Fault detection and diagnostics (FDD) layer 416 can be configured toprovide on-going fault detection for building subsystems 428, buildingsubsystem devices (i.e., building equipment), and control algorithmsused by demand response layer 414 and integrated control layer 418. FDDlayer 416 may receive data inputs from integrated control layer 418,directly from one or more building subsystems or devices, or fromanother data source. FDD layer 416 may automatically diagnose andrespond to detected faults. The responses to detected or diagnosedfaults can include providing an alert message to a user, a maintenancescheduling system, or a control algorithm configured to attempt torepair the fault or to work-around the fault.

FDD layer 416 can be configured to output a specific identification ofthe faulty component or cause of the fault (e.g., loose damper linkage)using detailed subsystem inputs available at building subsystemintegration layer 420. In other exemplary embodiments, FDD layer 416 isconfigured to provide “fault” events to integrated control layer 418which executes control strategies and policies in response to thereceived fault events. According to some embodiments, FDD layer 416 (ora policy executed by an integrated control engine or business rulesengine) may shut-down systems or direct control activities around faultydevices or systems to reduce energy waste, extend equipment life, orassure proper control response.

FDD layer 416 can be configured to store or access a variety ofdifferent system data stores (or data points for live data). FDD layer416 may use some content of the data stores to identify faults at theequipment level (e.g., specific chiller, specific AHU, specific terminalunit, etc.) and other content to identify faults at component orsubsystem levels. For example, building subsystems 428 may generatetemporal (i.e., time-series) data indicating the performance of BMS 400and the various components thereof. The data generated by buildingsubsystems 428 can include measured or calculated values that exhibitstatistical characteristics and provide information about how thecorresponding system or process (e.g., a temperature control process, aflow control process, etc.) is performing in terms of error from itssetpoint. These processes can be examined by FDD layer 416 to exposewhen the system begins to degrade in performance and alert a user torepair the fault before it becomes more severe.

Referring now to FIG. 5, a block diagram of another building managementsystem (BMS) 500 is shown, according to some embodiments. BMS 500 can beused to monitor and control the devices of HVAC system 100, watersidesystem 200, airside system 300, building subsystems 428, as well asother types of BMS devices (e.g., lighting equipment, securityequipment, etc.) and/or HVAC equipment.

BMS 500 provides a system architecture that facilitates automaticequipment discovery and equipment model distribution. Equipmentdiscovery can occur on multiple levels of BMS 500 across multipledifferent communications busses (e.g., a system bus 554, zone buses556-560 and 564, sensor/actuator bus 566, etc.) and across multipledifferent communications protocols. In some embodiments, equipmentdiscovery is accomplished using active node tables, which provide statusinformation for devices connected to each communications bus. Forexample, each communications bus can be monitored for new devices bymonitoring the corresponding active node table for new nodes. When a newdevice is detected, BMS 500 can begin interacting with the new device(e.g., sending control signals, using data from the device) without userinteraction.

Some devices in BMS 500 present themselves to the network usingequipment models. An equipment model defines equipment objectattributes, view definitions, schedules, trends, and the associatedBACnet value objects (e.g., analog value, binary value, multistatevalue, etc.) that are used for integration with other systems. Somedevices in BMS 500 store their own equipment models. Other devices inBMS 500 have equipment models stored externally (e.g., within otherdevices). For example, a zone coordinator 508 can store the equipmentmodel for a bypass damper 528. In some embodiments, zone coordinator 508automatically creates the equipment model for bypass damper 528 or otherdevices on zone bus 558. Other zone coordinators can also createequipment models for devices connected to their zone busses. Theequipment model for a device can be created automatically based on thetypes of data points exposed by the device on the zone bus, device type,and/or other device attributes. Several examples of automatic equipmentdiscovery and equipment model distribution are discussed in greaterdetail below.

Still referring to FIG. 5, BMS 500 is shown to include a system manager502; several zone coordinators 506, 508, 510 and 518; and several zonecontrollers 524, 530, 532, 536, 548, and 550. System manager 502 canmonitor data points in BMS 500 and report monitored variables to variousmonitoring and/or control applications. System manager 502 cancommunicate with client devices 504 (e.g., user devices, desktopcomputers, laptop computers, mobile devices, etc.) via a datacommunications link 574 (e.g., BACnet IP, Ethernet, wired or wirelesscommunications, etc.). System manager 502 can provide a user interfaceto client devices 504 via data communications link 574. The userinterface may allow users to monitor and/or control BMS 500 via clientdevices 504.

In some embodiments, system manager 502 is connected with zonecoordinators 506-510 and 518 via a system bus 554. System manager 502can be configured to communicate with zone coordinators 506-510 and 518via system bus 554 using a master-slave token passing (MSTP) protocol orany other communications protocol. System bus 554 can also connectsystem manager 502 with other devices such as a constant volume (CV)rooftop unit (RTU) 512, an input/output module (TOM) 514, a thermostatcontroller 516 (e.g., a TEC5000 series thermostat controller), and anetwork automation engine (NAE) or third-party controller 520. RTU 512can be configured to communicate directly with system manager 502 andcan be connected directly to system bus 554. Other RTUs can communicatewith system manager 502 via an intermediate device. For example, a wiredinput 562 can connect a third-party RTU 542 to thermostat controller516, which connects to system bus 554.

System manager 502 can provide a user interface for any devicecontaining an equipment model. Devices such as zone coordinators 506-510and 518 and thermostat controller 516 can provide their equipment modelsto system manager 502 via system bus 554. In some embodiments, systemmanager 502 automatically creates equipment models for connected devicesthat do not contain an equipment model (e.g., IOM 514, third partycontroller 520, etc.). For example, system manager 502 can create anequipment model for any device that responds to a device tree request.The equipment models created by system manager 502 can be stored withinsystem manager 502. System manager 502 can then provide a user interfacefor devices that do not contain their own equipment models using theequipment models created by system manager 502. In some embodiments,system manager 502 stores a view definition for each type of equipmentconnected via system bus 554 and uses the stored view definition togenerate a user interface for the equipment.

Each zone coordinator 506-510 and 518 can be connected with one or moreof zone controllers 524, 530-532, 536, and 548-550 via zone buses 556,558, 560, and 564. Zone coordinators 506-510 and 518 can communicatewith zone controllers 524, 530-532, 536, and 548-550 via zone busses556-560 and 564 using a MSTP protocol or any other communicationsprotocol. Zone busses 556-560 and 564 can also connect zone coordinators506-510 and 518 with other types of devices such as variable air volume(VAV) RTUs 522 and 540, changeover bypass (COBP) RTUs 526 and 552,bypass dampers 528 and 546, and PEAK controllers 534 and 544.

Zone coordinators 506-510 and 518 can be configured to monitor andcommand various zoning systems. In some embodiments, each zonecoordinator 506-510 and 518 monitors and commands a separate zoningsystem and is connected to the zoning system via a separate zone bus.For example, zone coordinator 506 can be connected to VAV RTU 522 andzone controller 524 via zone bus 556. Zone coordinator 508 can beconnected to COBP RTU 526, bypass damper 528, COBP zone controller 530,and VAV zone controller 532 via zone bus 558. Zone coordinator 510 canbe connected to PEAK controller 534 and VAV zone controller 536 via zonebus 560. Zone coordinator 518 can be connected to PEAK controller 544,bypass damper 546, COBP zone controller 548, and VAV zone controller 550via zone bus 564.

A single model of zone coordinator 506-510 and 518 can be configured tohandle multiple different types of zoning systems (e.g., a VAV zoningsystem, a COBP zoning system, etc.). Each zoning system can include aRTU, one or more zone controllers, and/or a bypass damper. For example,zone coordinators 506 and 510 are shown as Verasys VAV engines (VVEs)connected to VAV RTUs 522 and 540, respectively. Zone coordinator 506 isconnected directly to VAV RTU 522 via zone bus 556, whereas zonecoordinator 510 is connected to a third-party VAV RTU 540 via a wiredinput 568 provided to PEAK controller 534. Zone coordinators 508 and 518are shown as Verasys COBP engines (VCEs) connected to COBP RTUs 526 and552, respectively. Zone coordinator 508 is connected directly to COBPRTU 526 via zone bus 558, whereas zone coordinator 518 is connected to athird-party COBP RTU 552 via a wired input 570 provided to PEAKcontroller 544.

Zone controllers 524, 530-532, 536, and 548-550 can communicate withindividual BMS devices (e.g., sensors, actuators, etc.) viasensor/actuator (SA) busses. For example, VAV zone controller 536 isshown connected to networked sensors 538 via SA bus 566. Zone controller536 can communicate with networked sensors 538 using a MSTP protocol orany other communications protocol. Although only one SA bus 566 is shownin FIG. 5, it should be understood that each zone controller 524,530-532, 536, and 548-550 can be connected to a different SA bus. EachSA bus can connect a zone controller with various sensors (e.g.,temperature sensors, humidity sensors, pressure sensors, light sensors,occupancy sensors, etc.), actuators (e.g., damper actuators, valveactuators, etc.) and/or other types of controllable equipment (e.g.,chillers, heaters, fans, pumps, etc.).

Each zone controller 524, 530-532, 536, and 548-550 can be configured tomonitor and control a different building zone. Zone controllers 524,530-532, 536, and 548-550 can use the inputs and outputs provided viatheir SA busses to monitor and control various building zones. Forexample, a zone controller 536 can use a temperature input received fromnetworked sensors 538 via SA bus 566 (e.g., a measured temperature of abuilding zone) as feedback in a temperature control algorithm. Zonecontrollers 524, 530-532, 536, and 548-550 can use various types ofcontrol algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control a variable state or condition (e.g., temperature, humidity,airflow, lighting, etc.) in or around building 10.

Point Virtualization Under Online Meters

Referring now to FIG. 6-10, several drawings illustrating systems andmethods for point virtualization under online meters in a BMS are shown.In some embodiments, the point virtualization systems and methodsdescribed herein are implemented with BMS 400 or BMS 500, as describedwith reference to FIGS. 4-5.

Referring now to FIG. 6, a block diagram of a BMS 600 with pointvirtualization is shown. The BMS 600 includes multiple meters 602 thatprovide data samples for multiple real points measured by the meters 602(e.g., collected by sensors included with the meters 602). As usedherein, the term “real point” refers to a point that is measured orobserved by one or more of the meters 602. A real point may represent aphysical parameter of the building and/or building equipment served byBMS 600 (e.g., a temperature point measured by a temperature sensor ofthe meters 602, a power consumption measured by a power meter of themeters 602, a flow rate measured by a flow meter of the meters 602,etc.). Accordingly, the meters 602 provide raw data for real pointscorresponding to physical parameters of the building and/or buildingequipment served by the BMS 600. Conversely, the term “virtual point”refers to a point that is not directly measured by the meters 602 butrather is calculated or simulated based on one or more real points,other virtual points, and/or other parameters or values.

In many cases the real points measured by the meters 602 are notsufficient to allow the BMS 600 to calculate all metrics, keyperformance indicators, etc. desired by users of the BMS 600 ornecessary for implementing various features of the BMS 600. Thus, asdescribed in detail below, the BMS 600 provides for point virtualizationunder online meters 602 to provide an efficient, user-friendly, andcost-effective way to cover for deficiencies in the amount or type ofdata provided by the meters 602.

As shown in FIG. 6, the BMS 600 includes an analytics system 604 thatfacilitates point virtualization and provides for the calculation ofadvanced metrics (e.g., key performance indicators) based on both realpoints and virtual points. In some embodiments, the analytics system 604is a component of BMS 400 or BMS 500, for example included with systemmanager 502. As illustrated in FIG. 6, the analytics system 604 includesan object database 606, a point virtualization circuit 608, and anadvanced metrics circuit 610.

The object database 606 is configured to store data objectscorresponding to various elements and features of the BMS 600, forexample meter objects 612 and point objects 614. Each meter object 612is an electronic representation of one of the meters 602 in the BMS 600,and each point object 614 is an electronic representation of a realpoint (i.e., corresponding to a real-world measurement from a meter 602)or virtual point (i.e., corresponding to a simulated value not provideddirectly by a meter 602). Each point object 614 includes a set ofattributes associated with the corresponding point, and each meterobject includes a set of attributes associated with the correspondingmeter, as illustrated in FIG. 7 and described with reference theretobelow. For example, as an attribute of each meter object, the objectdatabase 606 may store a list of points associated with that meter.

The point virtualization circuit 608 is configured to create virtualpoint objects, store virtual point objects in the object database 606 aspoint objects 614, and alter the attributes of the meter objects 612 tolist virtual point objects 614 as associated with meter objects 612, forexample as described with reference to FIG. 8 below. The pointvirtualization circuit 608 thereby facilitates the creation of virtualpoints under online meters, i.e., such that a meter 602 may beassociated with both real points and virtual points. The pointvirtualization circuit 608 may also communicate with a user device(shown as client device 504). The point virtualization circuit 608 maygenerate a user interface for presentation on the user device (e.g.,tablet, laptop, desktop computer, smartphone) that allows the user torequest the creation of new virtual points, map virtual points to meters602, and define derivation formulas for virtual point objects. Examplesof such graphical user interfaces are shown in FIGS. 9-11 and describedin detail with reference thereto.

The advanced metrics circuit 610 is configured to calculate metrics(e.g., key performance indicators, roll-ups, space aggregations, faultdetection and diagnostics) relating to the building and/or buildingequipment served by the BMS 600. The advanced metrics circuit 610 mayreceive data from the meters 602 and determine a value for each pointassociated with each meter, including both virtual points and realpoints. The advanced metrics circuit 610 may then treat virtual pointsand real points identically to calculate metrics based on the values ofthe points. This may allow the advanced metrics circuit 610 to calculateall desired metrics even where the real points do not directlycorrespond to the inputs necessary to calculate that metric and withoutregard to whether the metric is calculated from real points, virtualpoints, or some combination thereof. In some embodiments, the advancedmetrics circuit 610 may receive a request to calculate a metric from aclient device 504, calculate the metric in response, and provide themetric to the client device 504 for presentation in a graphical userinterface.

As one illustrative example, a building may include a first space servedby a first meter and a second space served by a second meter. The firstmeter may collect a first real point for the first space correspondingto a physical parameter (e.g., power consumption), but the second metermay not be configured to collect data for that physical parameter. Insuch a situation, a second virtual point corresponding to the physicalparameter in the second space may be created under the second meter bycreating a virtual point object associated with a meter object for thesecond meter. Then, the advanced metrics circuit 610 may calculate anaggregate metric for the building (i.e., for the first space and thesecond space) using data for the first real point and data for thesecond virtual point. For example, the advanced metrics circuit 610 mayadd a value of the first real point to a value of second virtual pointto determine a total value for the building.

Referring now to FIG. 7, a block diagram of the object database 606 ofthe BMS 600 is shown, according to an exemplary embodiment. In someembodiments, the object database 606 is a component of BMS 400 or BMS500. The object database 606 can store meter objects 612 correspondingto each physical meter deployed in the buildings or facilities managedby the BMS 600, illustrated by an example meter object 616 in FIG. 7.The meter object 616 may include meter attributes including, forexample, the meter name (e.g., “M1”), meter location (e.g., “Building1—Floor 4”), and/or the points provided by that meter (e.g., “p1,” “p2,”and “p3”). The points listed in the meter object 616 may include bothreal points (i.e., points directly collected by the physical meter 602)and virtual points (i.e., simulated points calculated indirectly fromdata collected by one or more meters 602).

The object database 606 can also store a point object for each of one ormore points, including real points provided by a meter 602 and virtualpoints associated with a meter 602 in the object database 606. FIG. 6illustrates an example in which three point objects 618, 620, and 622(representing points “p1,” “p2,” and “p3” respectively) are associatedwith a meter object 616 (representing meter “M1”). Each point object618-622 includes attributes for the corresponding point, for example thepoint name, the point location, the point's units, and point type. Thepoint type may indicate whether the point corresponds to a physicalmeasurement or the point is a virtual point simulated within the BMS600. For a real point (i.e., a point corresponding to a physicalmeasurement), the point object 618-620 may include the point source,indicating the meter associated with the point. For a virtual point, thepoint object 622 may include a derivation formula which defines how adata series associated with the virtual point is derived from dataassociated with other points, from a model or simulation, or from basedon some other dataset.

FIG. 7 illustrates that the points attribute of the meter object 616 maylist both real points and virtual points. In the example shown, points“p1” and “p2” are real points whereas point “p3” is a virtual point. Asshown, by listing real points and virtual points together in the pointsattribute, the meter object 616 treats real and virtual point objectsidentically and makes no differentiation between real and virtualpoints. Virtual point objects such as point object 622 need not beorganized or stored under separate virtual meter objects or otherwisedifferentiated at the level of the meter objects 612. Instead, a virtualpoint object 622 is included under the meter object 616 to associate thevirtual point p3 with a physical meter M1, which is referred to hereinas point virtualization under online meters. The BMS 600 (e.g., theadvanced metrics circuit 610) may then use a virtual point like anyother point in calculating meter roll-ups and key performance indicatorsand generating displays of meter information for users. Pointvirtualization under online meters thereby facilitates calculation ofmetrics that require points not provided by real meters, improvesefficiency and reduces complexity relative to other potential ways tosimulate points (e.g., by creating virtual meters), and provides anintuitive framework that facilitates a user in understanding andconfiguring virtual points.

Referring now to FIG. 8, a flowchart of a process 800 for pointvirtualization under online meters is shown, according to an exemplaryembodiment. At step 802, the analytics system 604 associates a realpoint object for a real point with a meter object for an online meter602. The analytics system 604 stores the real point object and the meterobject in an object database 606. In some embodiments, the analyticssystem 604 associates the real point object with the meter object bylisting the real point object or a designation thereof (e.g., pointname) in a points attribute of the meter object. In some embodiments,the analytics system 604 associates the real point object with the meterobject by listing the meter object or a designation thereof (e.g., metername) in a meter attribute of the point objects.

At step 804, a virtual point is defined in the analytics system 604, forexample by a formula or other algorithm for calculating a value of thevirtual point. For example, the virtual point may be defined as afunction of real points, such that a value of the virtual point at agiven time step may be calculated based on the values of real points forthat time step (i.e., based on data collected by meters 602). Thevirtual point may also, or alternatively, be defined to have a valuegenerated by some other simulation, model, dataset, etc. In someembodiments, the analytics system 604 receives user input defining thevirtual point from a client device 504, for example as described withreference to FIGS. 9-11 below.

At step 806, the analytics system 604 associates the virtual point withthe meter object. The analytics system 604 may associate the virtualpoint with the meter object by listing the virtual point in an attributeof the meter object (e.g., a points attribute that lists the pointsassociated with the meter, including both virtual points and realpoints). The meter object may thereby treat virtual points and realpoints identically. Higher-level calculations, roll-ups, etc. may thensimply deal with all points in a similar or identical way, avoiding anycomputational complexity and expense that may be created by otherapproaches to point virtualization.

At step 808, the analytics system 604 receives a data sample from anonline meter 602 for the real point. For example, the analytics system604 receives an analog or digital signal, measurement, data value,sample, or other value of the real point from the online meter 602associated with the real point. At step 810, the analytics system 604assigns a value for the real point based on the data sample. Forexample, in an embodiment where the data sample is an analog signal, theanalytics system 604 may determine a digital representation of anumerical value of the real point based on the data sample and storethat representation as the value of the real point.

At step 812, a value for the virtual point is calculated based on thedefinition of the virtual point created at step 804. For example, thevirtual point may be calculated based on the data sample for the realpoint and/or based on data from other meters and/or other data sources(e.g., a weather forecast system, a building model simulation, abuilding schedule, etc.). For example, a virtual enthalpy point thatrepresents the enthalpy of a fluid can be calculated based on realpoints that represent the temperature and pressure of the fluid.

At step 814, the value for the real point from step 810 and the valuefor the virtual point from step 812 are associated with the meter 602.That is, based on the association of the real point and the virtualpoint with the meter 602 represented by the meter object (i.e., ascreated at step 802), the analytics system 604 associates the values forthe real point and the virtual point with the meter 602. At step 816,the analytics system 604 calculates a metric based on the valuesassociated with the meter 602, i.e., the value of the real point and thevalue of the virtual point. For example, the analytics system 604 mayadd, multiply, average, or perform other mathematical operations on thevalues to calculate the metric. As another example, the valuesassociated with the meter 602 may be used with values associated withone or more additional meters 602 to calculate a metric or a keyperformance indicator, or to generate a graphical representation of theoperation of building equipment. In all such calculations, the analyticssystem 604 treats the values in a substantially identical way, i.e.,without regard to the real or virtual nature of the points.

Referring now to FIG. 9, a meter configuration interface 900 for mappingand creating points under an online meter is shown, according to anexemplary embodiment. The meter configuration interface 900 may begenerated by the analytics system 604 (e.g., by the point virtualizationcircuit 608) of FIG. 6. The meter configuration interface 900 includes apoints tree widget 902, a meter distribution tree widget 904, and ameter details widget 906.

The points tree widget 902 includes search features 908, for exampleincluding drop down selections, list toggles, and/or a text searchfeature to allow a user to find and select any point already created inthe BMS 600. Search results may be presented in the points tree widget902. The points tree widget 902 thereby allows a user to search for andthen select a point to add the point to a meter using the meterdistribution tree widget 904

The meter distribution tree widget 904 provides a collapsible list 910of facilities and buildings. The collapsible list 910 indicates thatwithin each building are subcategories of building infrastructure (e.g.,electricity, weather) or building subspaces (e.g., Floor 2). Thecollapsible list 910 further includes entries for meters located withthe appropriate subcategory. Listed meters may include a statusindicator 912 that shows whether the meter is online, offline, orvirtual. A meter may be selected in order to add or delete a point underthat meter. In some embodiments, the meter distribution tree widget 904allows the user to move the meter to a different subcategory, building,or facility to reassign the meter. In some embodiments, the meterdistribution tree widget 904 allows the user to delete the meter fromthe collapsible list 910.

The meter details widget 906 allows a user to add a new meter, a newvirtual point, or a new online point. The meter details widget 906includes a type selection 914 that allows a user to select whether theywant to add a new meter, a new virtual point, or a new online point.When the user selects to add a new virtual point, the meter detailswidget displays entry fields 916 that accept input of a point name, apoint description, a unit type, a unit, a point role, and a series type.Some input fields may be indicated as optional, while others may beindicated as required for point creation. The meter details widget mayalso include a virtual point definition button 918, which is configuredto open a virtual point definition widget 1000 (shown in FIG. 10) whenselected by a user.

Referring now to FIG. 10, a virtual point definition widget 1000 isshown. Virtual point definition widget 1000 may be generated by theanalytics system 604 (e.g., by the point virtualization circuit 608) ofFIG. 6. The virtual point definition widget 1000 may include anequipment and meter tree 1002 that lists all equipment, meters, andexisting points, organized hierarchically. The virtual point definitionwidget 1000 also includes a formula entry portal 1004. The formula entryportal 1004 includes a formula field 1006, a numeric value entry field1008, and operator buttons 1010. A user may create a formula byselecting a point from the equipment and meter tree 1002 to add thepoint to the formula field 1006. The user may then select operatorbuttons 1010 to input mathematical operators (e.g., addition,multiplication, division) or logical operators (e.g., OR, AND, NOT, IF,<, >) to the formula field. The user may also input constant numericvalues into the formula field using the numeric value entry field 1008.The user may enter multiple existing points, multiple mathematical andlogical operators, and multiple constant numerical values into theformula field 1006 to craft a derivation formula for calculating thedata output of the new virtual point.

The virtual point definition widget 1000 may also include a validatesyntax button 1012. When the validate syntax button 1012 is selected,the analytics system 604 may check the derivation formula in the formulafield 1006 for syntax errors. Syntax errors include inoperablecombinations of mathematical symbols and failed logical expressions. Thesystem may check all possible point values for points in the formulafield to ensure the formula will not encounter any errors and/or willalways output a value for the virtual point. In some embodiments, thesystem highlights particular operators in the formula field that causeda syntax error or suggests corrections.

The virtual point definition widget 1000 may also include a save button1014. The save button 1014 may be configured to only be selectable afterthe analytics system 604 has validated the syntax of the derivationformula in the formula field. The save button 1014 allows the user tosave the derivation formula for a new virtual point and return to themeter configuration interface 900 shown in FIG. 9. The virtual pointdefinition widget 1000 may also be used to edit derivation formulas forexisting virtual points.

Referring now to FIG. 11, a building scorecard dashboard 1100 is shown,according to an exemplary embodiment. The building scorecard dashboard1100 includes a hierarchical navigation list 1102 of facilities,buildings, building subsystems or subareas, meters, and points. Meterson the navigation list may include a status indictor 1104 configured toshow whether that meter is online, offline, or virtual. Points listedunder meter include both real points and virtual points. When a meter isselected on the navigation list, a meter visualization widget 1106 maybe displayed on the building scorecard dashboard. The metervisualization widget 1106 may include a graphical representation of thedata associated with all points under the meter, include real andvirtual points. Time selection 1108 may be available in the upper rightcorner and can be switched easily between one week, one month, threemonths, six months, one year, and any custom range. The graphicaldisplay may then be adjusted to display data from the selected timerange. A grid toggle 1110 may also be available to easily switch betweenthe graphical display and a display of the meter data in a grid format.

The meter visualization widget 1106 presents data from a virtual pointin the same way it presents data from real points. The buildingscorecard dashboard 1100 may also include displays of building andfacility key performance indicators that include data roll-ups from allmeters in the buildings or facilities. Virtual points are treatedidentically to real points in these roll-up calculations and ingenerating visualizations for the building scorecard dashboard.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements can bereversed or otherwise varied and the nature or number of discreteelements or positions can be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepscan be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions can be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure can be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps canbe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed is:
 1. A building management system comprising: a meterconfigured to provide data samples of a real point, the real pointcorresponding to a first physical parameter measured by the meter; andan analytics circuit configured to: store a real point objectrepresenting the real point; store a meter object representing themeter, the meter object comprising a points attribute that lists one ormore point objects associated with the meter object including at leastthe real point object; and store a virtual point object representing avirtual point, the virtual point corresponding to a second physicalparameter not measured by the meter; and update the points attribute inthe meter object to list the virtual point object as one of the pointobjects associated with the meter object; receive a data sample of thereal point from the meter; calculate a value of the virtual point; andcalculate a metric based on the value of the virtual point.
 2. Thebuilding management system of claim 1, wherein the metric is calculatedbased on both the value of the virtual point and the data sample of thereal point from the meter.
 3. The building management system of claim 1,wherein the analytics circuit is configured to calculate the value ofthe virtual point using a formula stored in the virtual point object. 4.The building management system of claim 3, wherein the formula definesthe value of the virtual point as a function of the data sample of thereal point.
 5. The building management system of claim 3, wherein theformula defines the value of the virtual point as a function of one ormore data samples from one or more additional meters.
 6. The buildingmanagement system of claim 1, wherein the first physical parameter andthe second physical parameter characterize operation of buildingequipment.
 7. The building management system of claim 1, furthercomprising a system manager configured to control building equipmentbased on the value of the virtual point.
 8. A method for managing abuilding, comprising: collecting, by a meter, data samples of a realpoint, the real point corresponding to a first physical parametermeasured by the meter; storing a meter object representing the meter,the meter object comprising a points attribute that lists one or morepoint objects associated with the meter object; and storing a virtualpoint object representing a virtual point, the virtual pointcorresponding to a second physical parameter not measured by the meter;and updating the points attribute in the meter object to list thevirtual point object in as one of the point objects associated with themeter object: receiving a data sample of the real point from the meter;calculating a value of the virtual point; and calculating a metric basedon the value of the virtual point.
 9. The method of claim 8, whereincalculating the value of the virtual point comprises: storing a formulain the virtual point object; and calculating the value using theformula.
 10. The method of claim 9, comprising storing a real pointobject representing the real point, wherein real point is listed in thepoints attribute of the meter object.
 11. The method of claim 9, whereinthe formula defines the value of the virtual point as a function of thedata sample for the real point.
 12. The method of claim 9, wherein theformula defines the value of the virtual point as a function of one ormore data samples from one or more additional meters.
 13. The method ofclaim 9, wherein the first physical parameter and the second physicalparameter characterize operation of building equipment.
 14. The methodof claim 8, further comprising controlling building equipment based onthe value of the virtual point.
 15. A building management system,comprising: building equipment operable to affect a variable state orcondition of a building; a plurality of meters configured to collectdata samples of a plurality of real points relating to an operation ofthe building equipment; an analytics circuit configured to: generate agraphical user interface, the graphical user interface comprising: apoints tree widget comprising a list of the plurality of real points; ameter distribution tree widget comprising a list of the plurality ofmeters; and a meter details widget configured to allow a user to add avirtual point to the list of real points; receive data samples of theplurality of real points; calculate a value of the virtual point; andcalculate a metric based on the value of the virtual point.
 16. Thebuilding management system of claim 15, wherein the graphical userinterface comprises a virtual point definition widget configured toallow a user to input a formula that defines the virtual point.
 17. Thebuilding management system of claim 16, wherein the analytics circuit isconfigured to generate the value of the virtual point using the formulaand a first data sample of a first real point of the plurality of realpoints.
 18. The building management system of claim 16, wherein theanalytics circuit is configured to generate a graphical representationof an operation of the building equipment using the formula and the datasamples of the plurality of real points.
 19. The building managementsystem of claim 16, wherein the virtual point definition widgetcomprises: a formula field; a list of the plurality of real points, eachreal point on the list of real points selectable to add the real pointto the formula field; and a plurality of operator buttons, each operatorbutton selectable to add an operator to the formula field; wherein theformula comprises one or more real points and one or more operators todefine the virtual point as a function of the one or more real points.20. The building management system of claim 19, wherein the analyticscircuit is configured to check the formula input by the user for syntaxerrors.